Path Computation Element Method to Support Routing and Wavelength Assignment in Wavelength Switched Optical Networks

ABSTRACT

A network component comprising at least one processor configured to implement a method comprising transmitting a request to compute a routing assignment, a wavelength assignment, or both, wherein the request comprises a lightpath constraint indicator is disclosed. Also disclosed is an apparatus comprising a Path Computation Client (PCC) configured to transmit a request to and receive a reply from a Path Computation Element (PCE), wherein the request comprises a lightpath constraint, and wherein the reply comprises a routing assignment, a wavelength assignment, an error message, a no-path indication, or combinations thereof. Included is a method comprising receiving a request comprising a request parameter (RP) object comprising a lightpath constraint, sending a reply comprising a routing assignment, a wavelength assignment, an error message, a no-path indicator, or combinations thereof, wherein the request is received and the reply is sent using path computation element protocol (PCEP).

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional Patent Application Ser. No. 60/983,022 filed Oct. 26, 2007 by Lee et al. and entitled “Path Computation Element Method to Support Routing and Wavelength Assignment in Wavelength Switched Optical Networks,” which is incorporated herein by reference as if reproduced in its entirety.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

BACKGROUND

Wavelength division multiplexing (WDM) is one technology that is envisioned to increase bandwidth capability and enable bidirectional communications in optical networks. In WDM networks, multiple data signals can be transmitted simultaneously between network elements (NEs) using a single fiber. Specifically, the individual signals may be assigned different transmission wavelengths so that they do not interfere or collide with each other. The path that the signal takes through the network is referred to as the lightpath. One type of WDM network, a wavelength switched optical network (WSON), seeks to switch the optical signals with fewer optical-electrical-optical (OEO) conversions along the lightpath, e.g. at the individual NEs, than existing optical networks.

One of the challenges in implementing WDM networks is the determination of the routing and wavelength assignment (RWA) for the various signals that are being transported through the network at any given time. Unlike traditional circuit-switched and connection-oriented packet-switched networks that merely have to determine a route for the data stream across the network, WDM networks are burdened with the additional constraint of having to ensure that the same wavelength is not simultaneously used by two signals over a single fiber. This constraint is compounded by the fact that WDM networks typically use specific optical bands comprising a finite number of usable optical wavelengths. As such, the RWA continues to be one of the challenges in implementing WDM technology in optical networks.

SUMMARY

In one embodiment, the disclosure includes a network component comprising at least one processor configured to implement a method comprising transmitting a request to compute a routing assignment, a wavelength assignment, or both, wherein the request comprises a lightpath constraint indicator.

In another embodiment, the disclosure includes an apparatus comprising a Path Computation Client (PCC) configured to transmit a request to and receive a reply from a Path Computation Element (PCE), wherein the request comprises a lightpath constraint, and wherein the reply comprises a routing assignment, a wavelength assignment, an error message, a no-path indication, or combinations thereof.

In yet another embodiment, the disclosure includes a method comprising receiving a request comprising a request parameter (RP) object comprising a lightpath constraint, sending a reply comprising a routing assignment, a wavelength assignment, an error message, a no-path indicator, or combinations thereof, wherein the request is received and the reply is sent using path computation element protocol (PCEP).

These and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.

FIG. 1 is a schematic diagram of an embodiment of a WSON system.

FIG. 2 is a protocol diagram of an embodiment of the communications between a PCE and a PCC.

FIG. 3 is a schematic diagram of an embodiment of a PCE architecture.

FIG. 4 is a schematic diagram of another embodiment of the PCE architecture.

FIG. 5 is a schematic diagram of another embodiment of the PCE architecture.

FIG. 6 is a schematic diagram of an embodiment of a request parameter (RP) object.

FIG. 7A is a schematic diagram of an embodiment of a lightpath route parameter Type-Length-Value (TLV).

FIG. 7B is a schematic diagram of an embodiment of a lightpath route parameter object.

FIG. 8 is a schematic diagram of an embodiment of a tuning range TLV.

FIG. 9 is a schematic diagram of an embodiment of a wavelength selection preference TLV.

FIG. 10 is a schematic diagram of an embodiment of an objective function TLV.

FIG. 11 is a schematic diagram of an embodiment of a no path object.

FIG. 12 is a schematic diagram of an embodiment of a general-purpose computer system.

DETAILED DESCRIPTION

It should be understood at the outset that although an illustrative implementation of one or more embodiments are provided below, the disclosed systems and/or methods may be implemented using any number of techniques, whether currently known or in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.

Disclosed herein is a system and method for extending PCEP to accommodate RWA in WDM networks, such as the WSON. Specifically, a PCC may send a request to a PCE using PCEP. The request may include various types of lightpath constraints, such as a RWA computation option, a route parameter, a wavelength selection preference, an optimization degree, a timeliness characteristic, a duration, or combinations thereof. The lightpath constraints may be used in the computation of the RWA, and the RWA may be returned to the PCC using a PCEP reply. Alternatively, the PCEP reply may contain an error message or no path indicator if the RWA cannot be computed.

FIG. 1 illustrates one embodiment of a WSON system 100. The system 100 may comprise a WSON 110, a control plane controller 120, and a PCE 130. The WSON 110, control plane controller 120, and PCE 130 may communicate with each other via optical, electrical, or wireless means. The WSON 110 may comprise a plurality of NEs 112 coupled to one another using optical fibers. In an embodiment, the optical fibers may also be considered NEs 112. The optical signals may be transported through the WSON 110 over lightpaths that may pass through some of the NEs 112. In addition, some of the NEs 112, for example those at the ends of the WSON 110, may be configured to convert between electrical signals from external sources and the optical signals used in the WSON 110. Although four NEs 112 are shown in the WSON 110, the WSON 110 may comprise any number of NEs 112.

The WSON 110 may be any optical network that uses active or passive components to transport optical signals. The WSON 110 may implement WDM to transport the optical signals through the WSON 110, and may comprise various optical components as described in detail below. The WSON 110 may be part of a long haul network, a metropolitan network, or a residential access network.

The NEs 112 may be any devices or components that transport signals through the WSON 110. In an embodiment, the NEs 112 consist essentially of optical processing components, such as line ports, add ports, drop ports, transmitters, receivers, amplifiers, optical taps, and so forth, and do not contain any electrical processing components. Alternatively, the NEs 112 may comprise a combination of optical processing components and electrical processing components. At least some of the NEs 112 may be configured with wavelength converters, optical-electrical (OE) converters, electrical-optical (EO) converters, OEO converters, or combinations thereof. However, it may be advantageous for at least some of the NEs 112 to lack such converters as such may reduce the cost and complexity of the WSON 110. In specific embodiments, the NEs 112 may comprise optical cross connects (OXCs), photonic cross connects (PXCs), type I or type II reconfigurable optical add/drop multiplexers (ROADMs), wavelength selective switches (WSSs), fixed optical add/drop multiplexers (FOADMs), or combinations thereof.

The NEs 112 may be coupled to each other via optical fibers. The optical fibers may be used to establish optical links and transport the optical signals between the NEs 112. The optical fibers may comprise standard single mode fibers (SMFs) as defined in ITU-T standard G.652, dispersion shifted SMFs as defined in ITU-T standard G.653, cut-off shifted SMFs as defined in ITU-T standard G.654, non-zero dispersion shifted SMFs as defined in ITU-T standard G.655, wideband non-zero dispersion shifted SMFs as defined in ITU-T standard G.656, or combinations thereof. These fiber types may be differentiated by their optical impairment characteristics, such as attenuation, chromatic dispersion, polarization mode dispersion, four wave mixing, or combinations thereof. These effects may be dependent upon wavelength, channel spacing, input power level, or combinations thereof. The optical fibers may be used to transport WDM signals, such as course WDM (CWDM) signals as defined in ITU-T G.694.2 or dense WDM (DWDM) signals as defined in ITU-T G.694.1. All of the standards described herein are incorporated herein by reference.

The control plane controller 120 may coordinate activities within the WSON 110. Specifically, the control plane controller 120 may receive optical connection requests and provide lightpath signaling to the WSON 110 via Generalized Multi-Protocol Label Switching (GMPLS), thereby coordinating the NEs 112 such that data signals are routed through the WSON 110 with little or no contention. In addition, the control plane controller 120 may communicate with the PCE 130 using PCEP, provide the PCE 130 with information that may be used for the RWA, receive the RWA from the PCE 130, and/or forward the RWA to the NEs 112. The control plane controller 120 may be located in a component outside of the WSON 110, such as an external server, or may be located in a component within the WSON 110, such as a NE 112.

The PCE 130 may perform all or part of the RWA for the WSON system 100. Specifically, the PCE 130 may receive the wavelength or other information that may be used for the RWA from the control plane controller 120, from the NEs 112, or both. The PCE 130 may process the information to obtain the RWA, for example, by computing the routes, e.g. lightpaths, for the optical signals, specifying the optical wavelengths that are used for each lightpath, and determining the NEs 112 along the lightpath at which the optical signal should be converted to an electrical signal or a different wavelength. The RWA may include at least one route for each incoming signal and at least one wavelength associated with each route. The PCE 130 may then send all or part of the RWA information to the control plane controller 120 or directly to the NEs 112. To assist the PCE 130 in this process, the PCE 130 may comprise a global traffic-engineering database (TED), a RWA information database, an optical performance monitor (OPM), a physical layer constraint (PLC) information database, or combinations thereof. The PCE 130 may be located in a component outside of the WSON 110, such as an external server, or may be located in a component within the WSON 110, such as a NE 112.

In some embodiments, the RWA information may be sent to the PCE 130 by a path computation client (PCC). The PCC may be any client application requesting a path computation to be performed by the PCE 130. The PCC may also be any network component that makes such a request, such as the control plane controller 120, or any NE 112, such as a ROADM or a FOADM.

FIG. 2 illustrates an embodiment of a path computation communication method 200 between the PCC and the PCE. The method 200 may be implemented using any suitable protocol, such as the PCEP. In the method 200, the PCC may send a path computation request 202 to the PCE. The request may include any of the lightpath constraints disclosed below. At 204, the PCE calculates a path through the network that meets the lightpath constraints. For example, the PCE may calculate the RWA. The PCE may then send a path computation reply 206 to the PCC. The reply 206 may comprise the RWA or one of the other reply options described below.

When a network comprises a plurality of PCEs, not all PCEs within the network may have the ability to calculate the RWA. Therefore, the network may comprise a discovery mechanism that allows the PCC to determine the PCE in which to send the request 202. For example, the discovery mechanism may comprise an advertisement from a PCC for a RWA-capable PCE, and a response from the PCEs indicating whether they are RWA-capable. The discovery mechanism may be implemented as part of the method 200 or as a separate process.

The PCE may be embodied in one of several architectures. FIG. 3 illustrates an embodiment of a combined RWA architecture 300. In the combined RWA architecture 300, the PCC 310 communicates the RWA request and the required information to the PCE 320, which implements both the routing assignment and the wavelength assignment functions using a single computation entity, such as a processor. For example, the processor may process the RWA information using a single or multiple algorithms to compute the lightpaths as well as to assign the optical wavelengths for each lightpath. The amount of RWA information needed by the PCE 320 to compute the RWA may vary depending on the algorithm used. If desired, the PCE 320 may not compute the RWA until sufficient network links are established between the NEs or when sufficient RWA information about the NEs and the network topology is provided. The combined RWA architecture 300 may be preferable for network optimization, smaller WSONs, or both.

FIG. 4 illustrates an embodiment of a separated RWA architecture 400. In the separated RWA architecture 400, the PCC 410 communicates the RWA request and the required information to the PCE 420, which implements both the routing function and the wavelength assignment function using separate computation entities, such as processors 422 and 424. Alternatively, the separated RWA architecture 400 may comprise two separate PCEs 420 each comprising one of the processors 422 and 424. Implementing routing assignment and wavelength assignment separately may offload some of the computational burden on the processors 422 and 424 and reduce the processing time. In an embodiment, the PCC 410 may be aware of the presence of only one of two processors 422, 424 (or two PCEs) and may only communicate with that processor 422, 424 (or PCE). For example, the PCC 410 may send the RWA information to the processor 422, which may compute the lightpath routes and forward the routing assignment to the processor 424 where the wavelength assignments are performed. The RWA may then be passed back to the processor 422 and then to the PCC 410. Such an embodiment may also be reversed such that the PCC 410 communicates with the processor 424 instead of the processor 422.

In either architecture 300 or 400, the PCC may receive a route from the source to destination along with the wavelengths, e.g. GMPLS generalized labels, to be used along portions of the path. The GMPLS signaling supports an explicit route object (ERO). Within an ERO, an ERO label sub-object can be used to indicate the wavelength to be used at a particular NE. In cases where the local label map approach is used, the label sub-object entry in the ERO may have to be translated.

FIG. 5 illustrates a distributed wavelength assignment architecture 500. In the distributed wavelength assignment architecture 500, the PCE 510 may receive some or all of the RWA information from the NEs 520, 530, and 540, perhaps via direct link, and implements the routing assignment. The PCE 510 then directly or indirectly passes the routing assignment to the individual NEs 520, 530, and 540, which assign the wavelengths at the local links between the NEs 520, 530, and 540 based on local information. Specifically, the NE 520 may receive local RWA information from the NEs 530 and 540 and send some or all of the RWA information to the PCE 510. The PCE 510 may compute the lightpaths using the received RWA information and send the list of lightpaths to the NE 520. The NE 520 may use the list of lightpaths to identify the NE 530 as the next NE in the lightpath. The NE 520 may establish a link to the NE 530 and use the received local RWA information that may comprise additional constraints to assign a wavelength for transmission over the link. The NE 530 may receive the list of lightpaths from the NE 520, use the list of lightpaths to identify the NE 540 as the next NE in the lightpath, establish a link to the NE 540, and assign the same or a different wavelength for transmission over the link. Thus, the signals may be routed and the wavelengths may be assigned in a distributed manner between the remaining NEs in the network. Assigning the wavelengths at the individual NEs may reduce the amount of RWA information that has to be sent to the PCE 510.

As mentioned above, the request may comprise at least one lightpath constraint. The lightpath constraint may be any parameter that affects or limits the use of wavelengths along the lightpaths within the network. In an embodiment, the lightpath constraints may include a RWA computation option. The RWA computation option may specify the portions of the RWA that needs to be solved or otherwise considered. Suitable RWA computation options include routing assignment, wavelength assignment, routing and wavelength assignment, and routing assignment with a suggested or restricted wavelength set. Routing assignment may indicate that the NE desires the routing assignment, but not the wavelength assignment. Alternatively, routing assignment may indicate that the routing assignment is separated from the wavelength assignment, as indicated in FIG. 4 above. In either case, the request may also comprise the wavelength assignment. Wavelength assignment may indicate that the NE desires the routing assignment, but not the wavelength assignment. Alternatively, wavelength assignment may indicate that the wavelength assignment is separated from the routing assignment, as indicated in FIG. 4 above. In either case, the request may also comprise the routing assignment. Routing and wavelength assignment may indicate that the NE desires both the routing assignment and the wavelength assignment or a more optimal RWA. Finally, routing assignment with a suggested or restricted wavelength set may indicate that the NE desires the routing assignment and a suggested or restricted set of wavelengths such as candidate wavelengths from which the NE may select the wavelengths to assign to the lightpath(s). Alternatively, routing assignment with a suggested or restricted wavelength set may indicate that the wavelength assignment is distributed, as indicated in FIG. 5 above.

In a specific embodiment, the RWA computation option may be included in a request parameter (RP) object in the request. FIG. 6 illustrates one embodiment of a suitable RP object 600. The RP object 600 may include a reserved field 602, which is reserved for other purposes and may comprise the first about 9 bits of the RP object 600. The RP object 600 may also comprise a flags field 610 that may indicate various types of data and may comprise the subsequent about 23 bits. For example, the RWA computation option may be embodied as a RWA Computation (RC) flag 614 located in the flags field 610 of the RP object 600. The RC flag 614 may be about 2 bits in length and may be defined as indicated in Table 1 below.

TABLE 1 Bit Description 00 Routing Assignment 01 Wavelength Assignment 10 Routing Assignment with Suggested or Restricted Wavelength Set 11 Routing and Wavelength Assignment Alternatively, the RC flag 614 may be set to 01 to indicate wavelength assignment, 10 to indicate routing assignment, or 11 to indicate routing and wavelength assignment. FIG. 6 illustrates that the RP object 600 may also include any one or more of a directionality (I) 612 flag, a bidirectional (B) flag 616, or both. The I flag 612 and the B flag 616 are discussed below, while the remaining flags are described by the Internet Engineering Task Force (IETF) PCE Working Group Internet Drafts and Requests for Comments (RFCs), which are available at www.ietf.org/html.charters/pce-charter.html. The RP object 600 may also include a Request ID Number 620, which may be a unique identifier associated with the RP object 600. The RP object 610 may also include one or more optional TLVs 630 or objects such as the various TLVs and objects described below. As used herein, the terms “TLV” and “object” may both refer to any data structure that conveys any part or the entirety of a lightpath constraint.

In an embodiment, the lightpath constraints may include a route parameter. The route parameter may indicate a limitation in the assignment of wavelengths to the lightpath. Suitable route parameter options include bidirectional assignment of wavelengths, simultaneous assignment of wavelengths to a primary lightpath and a backup lightpath, and optical transmitter tuning range constraints. Bidirectional assignment of wavelengths may indicate that a single wavelength should be assigned to a lightpath and used for two-way communications or that separate wavelengths should be assigned to each direction of the lightpath. Simultaneous assignment of wavelengths to a primary lightpath and a backup lightpath may indicate that the same wavelength should be assigned to the primary lightpath and the backup lightpath. Alternatively, simultaneous assignment of wavelengths to a primary lightpath and a backup lightpath may indicate that separate wavelengths should be assigned to the primary lightpath and the backup lightpath. The optical transmitter tuning range constraint may indicate the wavelengths at which any optical transmitters along the lightpath can transmit.

In an embodiment, the RP object may indicate the route parameter. Specifically, the flags field 610 may include a bidirectional (B) flag 616, which may be about 1 bit in length in length. When the B flag 616 is set to zero, the request may be for a unidirectional Traffic Engineered Label Switched Path (TE LSP). When the B flag 616 may be set to one, the request is for a bidirectional TE LSP. When the B flag 616 is set to one, the flags field 610 may include a directionality (I) flag 612, which may comprise about 1 bit within the flags field 610. The I flag 612 may indicate the request is for a bidirectional wavelength assignment when set to one. The I flag 612 may indicate the request is for a unidirectional wavelength assignment when set to zero.

In a specific embodiment, the route parameter may be included in a lightpath route parameter (LRP) TLV, also known as a RP object, in the request. For example, when the RC flag described above indicates one of the three options comprising wavelength assignment, an optional LRP object, such as the LRP TLV, may be included with the RP object. FIG. 7A illustrates one embodiment of a suitable LRP TLV 700. The LRP TLV 700 may include a type field 702, a length field 704, and a value field 706. The type field 702 may comprise the first about 16 bits of the TLV 700, and may indicate that the LRP TLV 700 is a route parameter TLV. The length field 704 may be the subsequent about 16 bits of the LRP TLV 700, and may indicate the length of the value field 706. The value field 706 may be any size, but in some embodiments is the subsequent about 32 bits on the LRP TLV 700 and may indicate the route parameter. In an embodiment, the value field 706 is about 2 bits in length and may comprise a bidirectional (I) flag 708 and a same wavelength (S) flag 710. Alternatively, the value field 706 may be about one bit in length and may comprise the S flag 710. The I flag 708 may be about 1 bit in length, and may indicate the directionality of the wavelength assignment. For example, the LRP TLV 700 may indicate a bidirectional assignment of wavelengths when the I flag 708 is set to zero, and the LRP TLV 700 may indicate a unidirectional assignment of wavelengths when the I flag 708 is set to one. Similarly, the S flag 710 may be about 1 bit in length, and may indicate the commonality of the wavelength assignment. For example, the LRP TLV 700 may indicate an assignment of the same wavelength to the upstream direction and the downstream direction when the S flag 710 is set to zero, and the TLV 700 may indicate an assignment of different wavelengths to the upstream direction and the downstream direction when the S flag 710 is set to one.

In an embodiment, the lightpath constraints may include a timeliness characteristic. The timeliness characteristic may indicate the importance of timeliness to the request or how quickly the RWA should be calculated. Suitable optimization degree options include time critical, soft time bounds, and scheduled. Time critical may indicate that timeliness is important to the request, and may typically be used for restoration of network services or for other high-priority real-time service requests. Soft time bounds may indicate that timeliness is of moderate importance to the request. Soft time bound requests should be handled in a responsive manner, but may allow sufficient time for some amount of network optimization. Soft time bounds may typically be used for new or first-time connection requests. Scheduled may indicate that timeliness is not overly important to the request. Scheduled requests may be used for services requested prior to receipt of the signal, and may receive the highest degree of network optimization.

In an embodiment illustrated by FIG. 7B, a LRP object 750 may be included as a part of the request. The LRP object 750 may include a reserved field 752, which may be the first about 9 bits and may be used for other purposes. The LRP object 750 may also include a flags field 760, which may be the subsequent about 23 bits and may indicate various types of data. The flags field 760 may comprise a timeliness characteristic (TC) flag 762, which may be about 2 bits in length. The TC flag 762 may indicate the timeliness characteristic is time critical when the TC flag 762 is set to 11, the timeliness characteristic is soft time bounds when the TC flag 762 is set to 10, or the timeliness characteristic is scheduled when the TC flag 762 is set to 01. The LRP object 750 may also include a Request ID Number 770, which may be a unique identifier associated with the LRP object 750. The LRP object 750 may also include one or more optional TLVs or objects 780.

In a specific embodiment, the flags field 760 may also include an identical wavelength (I) flag 764 and a bidirectional (B) flag 766. The I flag 764 may be about 1 bit in length, and may indicate the assignment of an identical wavelength to a primary and a backup path. For example, the I flag 764 may indicate the assignment of an identical wavelength to a primary and a backup path when set to one, and the I flag 764 may indicate the assignment of different wavelengths to the primary and the backup path when set to zero. Similarly, the B flag 766 may be about 1 bit in length, and may indicate the commonality of the wavelength assignment. For example, the B flag 766 may indicate a bidirectional assignment of wavelengths when set to one, and the B flag 766 may indicate a unidirectional assignment of wavelengths when set to zero.

In an embodiment, the LRP object may include an optional transmitter tuning range TLV. FIG. 8 illustrates one embodiment of a suitable transmitter tuning range TLV 800. The TLV 800 may include a type field 802, a length field 804, and a value field 810. The type field 802 may comprise the first about 7 bits of the TLV 800, and may indicate that the TLV 800 is a tuning range TLV. The length field 804 may be variable in size, but in some embodiments may be the subsequent about 7 bits of the TLV 800, and may indicate the length of the value field 810. The value fields 810 may be any size, but in some embodiments is the latter-most about 64 bits of the TLV 800 and may indicate a lower bound 806 and an upper bound 808 for the transmitter tuning range.

In an embodiment, the lightpath constraints may include a wavelength selection preference. The wavelength selection preference may indicate the criteria by which the wavelength assignment is assigned to the lightpath. Suitable wavelength selection preference options include random, first fit, most used, least loaded, and no preference. Random may indicate that the wavelength should be randomly chosen from a group of suitable wavelengths. First fit may indicate that the wavelength should be the first suitable wavelength that is found. Most used may indicate that the selected wavelength should be the most commonly used wavelength within the group of all suitable wavelengths. Least loaded may indicate that the selected wavelength should be the least commonly used wavelength within the group of all suitable wavelengths. Finally, no preference may indicate that the PCC does not care or has no opinion as to the selected wavelength assignment.

In a specific embodiment, the wavelength selection preference may be included in a wavelength selection preference object in the request. For example, when the RC flag in the RP object described above indicates one of the three options comprising wavelength assignment, an optional wavelength selection preference object, such as a wavelength TLV, may be included with the RP object. FIG. 9 illustrates one embodiment of a suitable wavelength selection preference TLV 900. The TLV 900 may include a type field 902, a length field 904, and a value field 906. The type field 902 may comprise the first about 16 bits of the TLV 900, and may indicate that the TLV 900 is a wavelength selection TLV 900. The length field 904 may be the subsequent about 16 bits of the TLV 900, and may indicate the length of the value field 906. The value field 906 may be any size, but in some embodiments is the subsequent about 32 bits of the TLV 900 and may comprise a function code. The function code may indicate the wavelength selection preference as indicated in Table 2 below.

TABLE 2 Function Code Wavelength Selection Preference 1 Random 2 First Fit 3 Most Used 4 Least Loaded 5 No Preference

In a specific embodiment, the objective function may be included in an objective function object in the request. The objective function may specify the reason for or objective when implementing the routing assignment, wavelength assignment, or both. For example, when the RC flag in the RP object described above indicates one of the options comprising wavelength assignment, an optional objective function object, such as an objective function TLV, may be included with the RP object. FIG. 10 illustrates one embodiment of a suitable objective function TLV 1000. The TLV 1000 may include a type field 1002, a length field 1004, and a value field 1006. The type field 1002 may comprise the first about 16 bits of the TLV 1000, and may indicate that the TLV 1000 is a wavelength selection TLV 1000. The length field 1004 may be the subsequent about 16 bits of the TLV 1000, and may indicate the length of the value field 1006. The value field 1006 may be any size, but in some embodiments is the subsequent about 32 bits of the TLV 1000 and may comprise a function code. The function code may indicate the objective function as indicated in Table 3 below.

TABLE 3 Function Code Wavelength Selection Preference 1 Reduce or minimize the total number of links and/or wavelengths used 2 Reduce or minimize the maximum links and/or wavelengths used (load balance) 3 Reduce or minimize the path length of all flows

In an embodiment, the lightpath constraints may include an optimization degree. The optimization degree may indicate the number of lightpaths that are included in a single RWA calculation. Suitable optimization degree options include concurrent optimization, simultaneous request of a primary lightpath and a backup lightpath, or sequential optimization. Concurrent optimization may indicate that multiple lightpaths are contained in a single request. Simultaneous request of a primary lightpath and a backup lightpath may indicate that two lightpaths are requested: a primary lightpath that is intended to carry the signal, and a backup lightpath that can carry the signal if the primary lightpath fails. The primary and the backup lightpaths may have completely different routes, some common portions of their routes, or the same route. Similarly, the primary and the backup lightpaths may use completely different wavelengths, some common wavelengths if the network comprises at least one converter, or the same wavelength. While the primary and backup lightpaths may share some or all of their routing and wavelength assignment, the primary and backup lightpaths generally do not have the exact same routing and wavelength assignment. If desired, the request may indicate whether the primary and backup lightpaths are to share routing assignment, wavelength assignment, or both, as well as the extent of such. Sequential optimization may indicate that a single lightpath is contained in the request.

In an embodiment, the lightpath constraints may include a duration. The duration may indicate the length of the time in which the signal will be in service. Suitable duration options include dynamic, pseudo-static, and static. Dynamic may indicate that the signal will last a relatively short amount of time. Pseudo-static may indicate that the signal will last a moderate amount of time. Static may indicate that the signal will last a relatively long time.

After the request comprising the lightpath constraint has been received by the PCE, the PCE may issue a reply back to the PCC. The reply may include the RWA computed subject to the lightpath constraints indicated above. In addition, the reply may include any or all of the lightpath constraints that were contained in the request. If there is no RWA that satisfies the lightpath constraints, the reply may indicate such, for example using a no path indicator. Additionally or alternatively, the reply may indicate which parts of the RWA could not be obtained. For example, the reply may indicate that a suitable route could not be found, a suitable wavelength could not be found, or a suitable combination of a route and a wavelength could not be found. Finally, the reply may include a suggestion for relaxing the lightpath constraints to obtain the RWA. For example, if the RWA would have been obtainable but for the presence of one lightpath constraint, e.g. duration, then the reply may indicate such.

In a specific embodiment, the indication that RWA could not be obtained, any suggestions for relaxation of the lightpath constraints, or any combination thereof may be included in a no path object as illustrated by FIG. 11. The no path object 1100 may include a reserved field 1120 about 8 bits in length, which may be used for other purposes. The no-path object 1100 may also include a Nature of Issue (NI) field 1102, which comprises the first 8 bits of the no path object 1100. The NI field 1102 may indicate the nature of the issue that resulted in the RWA not being obtained. For example, a value equal to eight (0x08) may indicate that no path satisfying the set of constraints could be found. Similarly, a value equal to ten (0x10) may indicate that no wavelength was found associated with the RWA computation in the PC Reply message.

In a specific embodiment, a no path object 1100 may also include a flags field 1110 that may be about 16 bits in length. The flags field 1110 may comprise a plurality of flags. For example, the flags field 1110 may comprise an unsatisfied constraints (C) flag 1112 that may be about 1 bit in length and may indicate the reasons why a path could not be found. For example, the C flag 1112 indicates a set of unsatisfied constrains when the C flag 1112 is set to one. When the flag is set to zero, the C flag 1012 indicates no reason why a path could not be found.

In yet another embodiment, the no path object 1100 may include one or more optional TLVs 1130. For example, the no path object 1100 may include a no path vector TLV in the no path object 1100. For example, a 0x10 bit flag may be set to one in the no path vector TLV to indicate that no route, wavelength, or both was found that satisfied the lightpath constraints in the request. In another example, a 0x08 bit flag may indicate that no path was found.

In an embodiment, the reply may include at least one message. For example, if the PCE is not configured to calculate a RWA, then the reply may contain an error message that the PCE is not configured to calculate the RWA. Such an error message may contain a PCEP error object and an error-value, such as error-type=15 and the error-value=1. Alternatively, if the request is not compliant with administrative privileges, then the reply may contain an error message that indicates that the request is not compliant with administrative privileges. Such an error message may contain a PCEP-error object and an error-value, such as the error-type=6 and the error-value=3. Further in the alternative, if the request or the RWA violates some policy within the PCE or the WSON, then the reply may contain an error message that indicates the policy violation. Such an error message may contain a PCEP error object, such as error-type=6. In any event, the request may be cancelled, and a new request may have to be sent to the PCE.

The network components described above may be implemented on any general-purpose network component, such as a computer or network component with sufficient processing power, memory resources, and network throughput capability to handle the necessary workload placed upon it. FIG. 12 illustrates a typical, general-purpose network component 1200 suitable for implementing one or more embodiments of the components disclosed herein. The network component 1200 includes a processor 1202 (which may be referred to as a central processor unit or CPU) that is in communication with memory devices including secondary storage 1204, read only memory (ROM) 1206, random access memory (RAM) 1208, input/output (I/O) devices 1210, and network connectivity devices 1212. The processor 1202 may be implemented as one or more CPU chips, or may be part of one or more application specific integrated circuits (ASICs).

The secondary storage 1204 is typically comprised of one or more disk drives or tape drives and is used for non-volatile storage of data and as an over-flow data storage device if RAM 1208 is not large enough to hold all working data. Secondary storage 1204 may be used to store programs that are loaded into RAM 1208 when such programs are selected for execution. The ROM 1206 is used to store instructions and perhaps data that are read during program execution. ROM 1206 is a non-volatile memory device that typically has a small memory capacity relative to the larger memory capacity of secondary storage 1204. The RAM 1208 is used to store volatile data and perhaps to store instructions. Access to both ROM 1206 and RAM 1208 is typically faster than to secondary storage 1204.

While several embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods might be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented.

In addition, techniques, systems, subsystems, and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein. 

1. A network component comprising: at least one processor configured to implement a method comprising: transmitting a request to compute a routing assignment, a wavelength assignment, or both, wherein the request comprises a lightpath constraint indicator.
 2. The network component of claim 1, wherein the request comprises a request parameter (RP) object, and wherein the lightpath constraint indicator comprises a routing and wavelength assignment computation (RC) flag in the RP object.
 3. The network component of claim 2, wherein the RC flag indicates: a routing assignment and a wavelength assignment when the RC flag is set to 11, the wavelength assignment but not the routing assignment when the RC flag is set to 01, the routing assignment with a suggested wavelength set or a restricted wavelength set when the RC flag is set to 10, or the routing assignment but not the wavelength assignment when the RC flag is set to
 00. 4. The network component of claim 1, wherein the request comprises a lightpath request parameter (LRP) object, and wherein the lightpath constraint indicator comprises a bidirectional (B) flag in the LRP object and a directionality (I) flag in the LRP object.
 5. The network component of claim 4, wherein the B flag indicates a bidirectional Traffic Engineered Label Switched Path (TE LSP) when the B flag is set to 1 or a unidirectional TE LSP when the B flag is set to 0, and wherein the I flag indicates a bidirectional wavelength assignment when set to 1 or a unidirectional wavelength assignment when set to
 0. 6. The network component of claim 1, wherein the request comprises a LRP object, and wherein the lightpath constraint indicator comprises a directionality (I) bit in the LRP object and a same wavelength (S) bit in the LRP object.
 7. The network component of claim 6, wherein the I bit indicates a bidirectional assignment of wavelengths to a primary path and a backup path when the I bit is set to 0 or a unidirectional assignment of wavelengths to the primary path and the backup path when the I bit is set to 1, and wherein the S bit indicates an assignment of the same wavelength to the upstream direction and the downstream direction when the S bit is set to 0 or an assignment of different wavelengths to the upstream direction and the downstream direction when the S bit is set to
 1. 8. The network component of claim 1, wherein the lightpath constraint indicator comprises a wavelength selection preference Type-Length-Value (TLV) comprising a wavelength selection preference function code that indicates whether the wavelength selection preference is random, first fit, most used, least loaded, or no preference.
 9. The network component of claim 8, wherein the wavelength function code indicates: a random wavelength selection preference when the function code is set to 1, a first fit wavelength selection preference when the function code is set to 2, a most used wavelength selection preference when the function code is set to 3, a least loaded wavelength selection preference when the function code is set to 4, or no wavelength selection preference when the function code is set to
 5. 10. The network component of claim 4, wherein the request comprises a lightpath request parameter (LRP) object, and wherein the lightpath constraint indicator comprises a timeliness characteristic (TC) flag in the LRP object.
 11. The network component of claim 10, wherein the TC flag indicates: the timeliness characteristic is time critical when the TC flag is set to 11, the timeliness characteristic is soft time bounds when the TC flag is set to 10, or the timeliness characteristic is scheduled when the TC flag is set to
 01. 12. The network component of claim 1, wherein the request comprises a LRP object, and wherein the lightpath constraint indicator comprises a route parameter TLV indicating a transmitter tuning range, wherein route parameter TLV comprises an upper bound, a lower bound, or both.
 13. The network component of claim 1, wherein the request comprises an objective function object.
 14. The network component of claim 13, wherein the objective function object comprises an objective function value, wherein the objective function object indicates a reduced or minimized number of links and/or wavelengths when the objective function value is set to one, wherein the objective function indicates load balancing of links and/or wavelengths when the objective function value is set to two, and wherein the objective function indicates a reduced or minimized path length for a plurality of flows when the objective function value is set to two.
 15. An apparatus comprising: a Path Computation Client (PCC) configured to transmit a request to and receive a reply from a Path Computation Element (PCE), wherein the request comprises a lightpath constraint, and wherein the reply comprises a routing assignment, a wavelength assignment, an error message, a no-path indication, or combinations thereof.
 16. The apparatus of claim 15, wherein the error message indicates that the PCE is not capable of routing and wavelength assignment.
 17. The apparatus of claim 16, wherein the routing and wavelength assignment incapability of the PCE is indicated by an error-type equal to about 15 and an error-value equal to about
 1. 18. The apparatus of claim 15, wherein the error message indicates a policy violation.
 19. The apparatus of claim 18, wherein the policy violation is indicated by an error-type equal to about 6 and an error-value equal to about
 3. 20. A method comprising: receiving a request comprising a request parameter (RP) object comprising a lightpath constraint; sending a reply comprising a routing assignment, a wavelength assignment, an error message, a no-path indicator, or combinations thereof, wherein the request is received and the reply is sent using path computation element protocol (PCEP).
 21. The method of claim 20, wherein the no-path indicator comprises a TLV indicating that no wavelength was found.
 22. The method of claim 21, wherein the no-path indicator comprises one or more of: a 0x08 flag that indicates that no path was found when set to one; or a 0x10 flag that indicates that no wavelength satisfying the constraints of the request was found. 